Conversation
|
👋 Thanks for assigning @jkczyz as a reviewer! |
| @@ -6,12 +6,10 @@ source "$(dirname "$0")/ci-tests-common.sh" | |||
|
|
|||
| echo -e "\n\nChecking and testing lightning with features" | |||
There was a problem hiding this comment.
If you remove the check part, you might want to update the printed message here and elsewhere to remove the Checking part.
There was a problem hiding this comment.
Removed. I left it in place in ci-tests-sync.sh, because there is still some only-checking in non CI.
|
|
||
| if [ -z "$CI_ENV" ] && [[ -z "$BITCOIND_EXE" || -z "$ELECTRS_EXE" ]]; then | ||
| echo -e "\n\nSkipping testing Transaction Sync Clients due to BITCOIND_EXE or ELECTRS_EXE being unset." | ||
| cargo check -p lightning-transaction-sync --tests |
03629f0 to
6b0eeea
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4459 +/- ##
==========================================
+ Coverage 85.97% 86.09% +0.12%
==========================================
Files 159 159
Lines 104722 105185 +463
Branches 104722 105185 +463
==========================================
+ Hits 90030 90559 +529
+ Misses 12191 12115 -76
- Partials 2501 2511 +10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
jkczyz
left a comment
There was a problem hiding this comment.
Review courtesy of Claude
| # shellcheck source=ci/ci-tests-common.sh | ||
| source "$(dirname "$0")/ci-tests-common.sh" | ||
|
|
||
| echo -e "\n\nChecking and testing Block Sync Clients with features" |
There was a problem hiding this comment.
I left it in place (#4459 (comment)), but also fine with removing. Removed.
ci/ci-tests-workspace.sh
Outdated
| cargo check --tests --quiet --color always | ||
|
|
||
| WORKSPACE_MEMBERS=( $(cat Cargo.toml | tr '\n' '\r' | sed 's/\r //g' | tr '\r' '\n' | grep '^members =' | sed 's/members.*=.*\[//' | tr -d '"' | tr ',' ' ') ) | ||
|
|
||
| echo -e "\n\nTesting the workspace, except lightning-transaction-sync." | ||
| echo -e "\n\nTesting the workspace." | ||
| cargo test --quiet --color always |
There was a problem hiding this comment.
I think the goal is to fail as fast as possible - perhaps 🤷♂️
| cargo check -p lightning-transaction-sync --tests --quiet --color always --features esplora-async-https | ||
| cargo check -p lightning-transaction-sync --tests --quiet --color always --features electrum | ||
| else | ||
| echo -e "\n\nTesting Transaction Sync Clients with features." |
There was a problem hiding this comment.
Should this also test without any features?
There was a problem hiding this comment.
We should indeed be consistent. The crate doesn't contains anything without a feature it seems (lib.rs), but maybe we do want to check that it doesn't error. Added the test without features. diff
ab5a336 to
c0cdaaa
Compare
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
|
🔔 2nd Reminder Hey @tnull! This PR has been waiting for your review. |
TheBlueMatt
left a comment
There was a problem hiding this comment.
cargo check does something different than cargo test. It doesn't check with test-specific features enabled and thus can catch bugs where we have code that only builds with test features. I don't think these should be removed (they're also incredibly cheap).
Replace the per-member cargo check + cargo doc loop with a single `cargo doc --workspace` call. The per-member cargo check is redundant with the workspace-level cargo check already run earlier in the script. Also remove the separate `cargo test -p lightning-custom-message` which is covered by the workspace-level cargo test. Fix stale "except lightning-transaction-sync" echo messages, as it has been a workspace member for a while now. AI tools were used in preparing this commit.
c0cdaaa to
b35a849
Compare
I think you mean cargo check checks That leaves just the workspace build simplification. |
No description provided.